List of Flash News about 21 million supply
| Time | Details |
|---|---|
|
2025-12-11 18:08 |
Dan Held on Unlimited Fiat vs 21M BTC: Hard Cap Facts and Liquidity Signals Traders Should Watch
According to @danheld, the core bet is unlimited fiat supply competing for a fixed 21 million BTC, putting Bitcoin’s programmed scarcity at the center of the trade thesis. Source: @danheld (X, Dec 11, 2025). Bitcoin’s maximum supply is hard-capped at 21 million by consensus rules, with issuance reduced via halvings every 210,000 blocks until roughly 2140. Source: Bitcoin.org Developer Guide and BIP-42 (Bitcoin Core). Fiat money supply is elastic and can be expanded by central banks through tools like asset purchases and lending facilities, affecting purchasing power via policy and credit growth. Source: Board of Governors of the Federal Reserve System education resources and IMF monetary policy primers. For trading, a fixed BTC supply means marginal demand from regulated vehicles such as US spot BTC ETFs can have outsized price impact when liquidity expands. Source: U.S. SEC approval of spot Bitcoin ETFs on Jan 10, 2024 and related SEC orders. Effective tradable float may be lower than 21 million due to provably lost or long-dormant coins, reducing immediate market supply. Source: Chainalysis estimate of 2.78 to 3.79 million lost coins (2017 report). Key liquidity indicators traders monitor for BTC risk exposure include global M2 growth, USD strength via DXY, and U.S. real yields from TIPS. Source: World Bank Broad Money (M2) dataset, ICE U.S. Dollar Index methodology, and U.S. Treasury real yield data. Research frameworks emphasize liquidity and real yields as major drivers of Bitcoin performance, supporting process-driven entries and sizing beyond narratives alone. Source: Fidelity Digital Assets Bitcoin First (2022) and ARK Invest Bitcoin Monthly research. |
|
2025-12-06 17:25 |
BTC vs Gold: CZ vs Peter Schiff at Binance Blockchain Week — 5 Trading Takeaways on Tokenized Gold, Scarcity (21M), and Utility
According to @cas_abbe, the CZ–Peter Schiff debate at Binance Blockchain Week centered on whether tokenized vault-backed gold can rival BTC’s open, permissionless settlement, with Schiff promoting tokenized gold as digital money and CZ arguing tokenization does not solve the problems Bitcoin already solved; source: @cas_abbe on X, Dec 6, 2025. According to @cas_abbe, CZ contrasted Bitcoin’s auditable 21 million cap with the unknown total and future mined supply of gold and the potential risk of synthetic gold, while Schiff replied that gold supply grows slowly; source: @cas_abbe on X, Dec 6, 2025. According to @cas_abbe, Schiff stressed that central banks accumulate gold and none accumulate BTC, whereas CZ argued that markets move faster than central bank adoption; source: @cas_abbe on X, Dec 6, 2025. According to @cas_abbe, CZ cited real-world BTC usage in Africa, BTC‑denominated contracts on Binance, and faster, cheaper global payments, while Schiff claimed BTC is mostly speculative and not a pricing unit; source: @cas_abbe on X, Dec 6, 2025. According to @cas_abbe, key trading takeaways from the debate are the scarcity predictability of BTC, the open global settlement utility versus digital movement in tokenized gold, and the institutional adoption gap highlighted by central bank gold preference; source: @cas_abbe on X, Dec 6, 2025. |
|
2025-08-13 09:28 |
OKX Completes 65,256,712 OKB Token Burn: Etherscan Shows 279M in Burn Address, Supply Now 21M OKB
According to @EmberCN, OKX has completed the transfer of the announced 65,256,712 OKB into the burn address about 10 minutes before the post, finalizing the burn event (source: @EmberCN). On-chain data indicates the burn wallet now holds roughly 279 million OKB, implying approximately 21 million OKB remain outstanding, as noted by @EmberCN and visible on the OKB token page on Etherscan (source: @EmberCN; Etherscan). This materially reduces outstanding supply and alters float-based valuation and liquidity metrics that traders monitor, based on the updated on-chain totals reported by Etherscan and the update from @EmberCN (source: Etherscan; @EmberCN). |